System and method enabling mobile near-field communication to update display on a payment card

ABSTRACT

Disclosed are a system and methods enabling updating of a card number of a payment card and thereby reissuing the payment card utilizing a reissue application associated with the payment card. The reissue application, when executed communicates with a service provider that manages the payment card. The payment card includes processing circuitry and a rewriteable visual display. Using cryptographic techniques, the reissue application and payment card are authenticated to the service provider. Upon verification, an updated card number is obtained and provided via near-field communication to the payment card. In response to the update payment card number received from the reissue application, the rewriteable visual display on the payment card is updated with the updated card number. Other information may also be presented on the rewriteable visual display of the payment card based on user preferences.

BACKGROUND

Payment cards, such as credit cards, gift cards and debit cards, havebecome a preferred payment method in transactions. The number oftransactions involving payment cards is increasing at an incrediblerate. The number of fraudulent transactions is also increasing at anincredible rate. As a result, the number of payment cards that must bereplaced is increasing as well. A payment card may have once been aninexpensive item, but with the security features required today the costof a payment card is not trivial. The cost is particular high to cardissuers when multiplied by the many card replacements that occur everyyear.

SUMMARY

Disclosed is a method including a step of sending, via a mobile device,a request to update a card number on a payment card to be reissued. Therequest may include an indication that a card number presented on adisplay of the payment card and encoded on a magnetic strip of thepayment card is invalid and unusable. In response to the sent request,the mobile device may receive an authorization to reissue the card andupdate the card number. In response to the received authorization, anupdated card number may be obtained from a secure source of updated cardnumbers. In response to command signals from a reissue applicationexecuting on the mobile device, an updated card number signalrepresenting the updated card number may be output via a near-fieldcommunication circuit in the mobile device. In response to outputtingthe updated card number signal, a signal indicating that updating of thecard number was successful is received via a near-field communicationcircuit in the mobile device.

Disclosed is another method that includes emitting, by a near-fieldcommunication device of a payment card, an authentication signal forreceipt by a near-field communication device of a mobile device. Theemitted authentication signal includes a card number currently displayedon the payment card. The emitted authentication signal may be emittedafter the payment card is introduced into any portion of a near-fieldcommunication electric field surrounding the mobile device. The emittedauthentication signal may be an approval of a request to change the cardnumber currently displayed on a visual display of the payment card.While the payment card remains within any portion of the near-fieldcommunication electric field surrounding the mobile device, the methodmay include receiving, by a near-field communication device of thepayment card, an updated card number signal. The updated card numbersignal may contain an updated card number. In response to receiving theupdated card number signal, the card number currently displayed on thevisual display of the payment card may be replaced with the updated cardnumber.

Disclosed is an example of a system including a reissue application on amobile device, an authentication server, and a payment card. The reissueapplication may be executable by a processor of the mobile device andwhen executed is operable to reissue a card number of the payment card.The authentication server is operable to communicate with the reissueapplication. The payment card may include a payment card near-fieldcommunication device, a rewriteable visual display, a processor, and amemory. The rewriteable visual display of the payment card may beoperable to present a prior-issued card number. The reissue application,when executed may be operable to send a request to the authenticationserver to verify that the reissue application is associated with thepayment card. In response to a verification that the reissue applicationis associated with the payment card, the reissue application may obtainan updated card number. The updated card number is different from theprior-issued card number. The signal generation component of the reissueapplication generates an updated card number signal. The updated cardnumber signal may further include information related to at least oneof: a card verification value, an expiration date, or an issuer. Thereissue application may cause the updated card number signal to beoutput. The payment card may be operable to receive, via the paymentcard near-field communication device, the updated card number signal.Based on the updated card number signal, the rewriteable visual displaymay be driven to present an updated card number in place of theprior-issued card number.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a system operable to reissue a payment cardaccording to an example;

FIG. 2 is an example of a contactless card suitable for use in thesystem example of FIG. 1;

FIG. 3A is a block diagram illustrating examples of components of thecontactless card of FIG. 2;

FIG. 3B illustrates an example of an apparatus that supplies power to apayment card for modifying a rewriteable visual display of a paymentcard example as described with reference to FIGS. 2 and 3A;

FIG. 4 is a flow chart of an example process performed by a mobiledevice using in a system such as that illustrated in FIG. 1;

FIG. 5 is a flow chart illustrating an example of a process executed byone or more components of the system example of FIG. 1; and

FIG. 6 illustrates a computer architecture suitable for implementing oneor more components of the system example of FIG. 1.

DETAILED DESCRIPTION

Various examples describe a system and methods that enable updating of acard number of a payment card and thereby reissuing the payment cardutilizing a mobile device associated with the payment card. The mobiledevice hosts a reissue application that is a mobile computer applicationthat executes on a processor of the mobile device operable tocommunicate with a service provider that manages the payment card. Thepayment card includes processing circuitry and a rewriteable visualdisplay. Using cryptographic techniques, the mobile device and paymentcard are authenticated to the service provider. Upon verification, anupdated card number is obtained from a secure source and provided vianear-field communication by the mobile device to the payment card. Inresponse to the update payment card number received from the mobiledevice, the rewriteable visual display on the payment card is updatedwith the updated card number. Other information may also be presented onthe rewriteable visual display of the payment card based on userpreferences. The benefits of the disclosed examples include mobilereissuance of a payment card, reduced wait time to receive an updatedcard number, increased security based on security features of both themobile device and the payment card, and other benefits that may beapparent upon review and consideration of the disclosed examples.

In the described examples, the payment card may be a contactless card ofcredit-card dimension including an embedded integrated circuit, astorage device and an interface that permits the card to communicatewith a receiving device using a Near Field Communication (NFC) protocol.An example of contactless payment card that may be used in the disclosedexamples is described in U.S. patent application Ser. No. 16/205,119filed Nov. 29, 2018 by Osborn, et. al, entitled “Systems and Methods forCryptographic Authentication of Contactless Cards” and is incorporatedherein by reference in its entirety (hereinafter the '119 Application).

FIG. 1 is a block diagram of a system operable to reissue a payment cardaccording to an example. The system 100 may include a service provider105, a mobile device 120, a data network 130, and a payment card 110.

The data network 130 may be a cellular network, a wide area network(WAN), the Internet, a Wi-Fi network, or a combination of differentnetworks. The service provider 105 may include a data storage device 101coupled to a payment account server 103, an application server 106, aservice provider network 107, and an authentication server 150. Serviceprovider 105 may be, in one example, a business providing computer-basedservices to clients over a network 115. The combination of the softwareand hardware that provides a particular service of the service providerto a client is referred to herein as a “server.” The servers maycommunicate over a private network 125 of the service provider, oftenreferred to as a service provider network 107. The service providernetwork 107 may comprise a wireless network, a wired network or anycombination of wireless network and wired network as described abovewith regard to data network 130.

In the system of FIG. 1, service provider 105 is shown to include anapplication server 106 and an authentication server 150. Although eachserver is illustrated as a discrete device, it is appreciated that theapplications and servers may be distributed throughout the enterpriseor, in the case of distributed resources such as “cloud” resources,throughout the service provider network 107. The application server 106may support one or more application services provided by the serviceprovider 105, for example, an account management service. Theauthentication server 150, according to one aspect, may be operable toprovide one or both of first factor authentication and second factorauthentication using the contactless card as disclosed in more detailbelow.

Data storage device 109 comprises data storage resources that may beused, for example, to store customer account, credential and otherauthentication information, including dynamic password data, for use bythe application server 106 and the authentication server 150. The datastorage device 109 may be comprised of coupled data resources comprisingany combination of local storage, distributed data center storage orcloud-based storage.

The service provider network 107 may be a wide area data communicationnetwork or the like, that enables the various components of the serviceprovider 105 to communicate with one another within the service provider105 and the data network 130 outside the service provider 105. Thepayment account server 103 may be coupled to a data storage device 101and communicatively coupled to the data network 130 and theauthentication server 150. The payment account server 103 may beoperable to store payment account information 102 related to the paymentcard 110 as well as other payment cards (not shown) in data storagedevice 101. For example, the payment account information 102 may includeat least one of: a payment account balance, payment account limits,information related to the mobile device 120, user preferenceinformation, such as user prefernce selections, transaction information,a payment card number history, a list of undeployed payment cardnumbers, information related to users authorized to use the payment card110, or the like.

In some examples, the payment account server 103 may be operable tostore the updated card number 129. For example, in response to a requestfrom the mobile device 120, the payment account server 103 may beoperable to retrieve the updated card number 129 from the data storagedevice 101 and send the updated card number 129 to the reissueapplication 127 executing on the mobile device 120.

The application server 106 may be operable to manage the operation anddelivery of different applications (i.e., computer applications orprogramming code), such as the reissue application 127 that areexecutable by a processor on a mobile device, a server or anothercomputing device. For example, a user may select an icon, link or othermechanism provided as part of the reissue application 127 to launch theapplication on the mobile device 120 to access payment card numberreissue services. The application server 106 may maintain userpreferences, user names, or similar information in a data storage (notshown) that may be similar to data storage device 101.

The authentication server 150 may include hardware and software forperforming various authentication processes. The authentication server150 is operable to communicate with the payment account server 103 andthe application server 106 within the service provider 105. For example,the authentication server 150 may provide an authentication status withrespect to a payment card that is having a card number reissued inresponse to a request from either the payment account server 103 or theapplication server 106. In addition, the mobile device 120 and the datanetwork 130 are operable to exchange communications between the mobiledevice 120 and the authentication server 150.

In an example, the authentication server 150 may be operable toauthenticate transactions made with the payment card and operationsrelated to the payment card, such as reissuing a payment card number,authenticating account information updates, or the like. For example,the authentication server 150 may be operable to store informationrelated to clients of the service provider 105 including a clientinformation table (not shown). The information may also be stored indata storage device 101 and be accessible to the payment account server103. Such information may include, but is not limited to, the clientusername and client cryptogram keys and counters.

The mobile device 120 may include a mobile device processor 124, amemory 122 storing a reissue application 127, transceivers (XCVRS) 187,and a near-field communication (NFC) device 125. The mobile device 120may include a secure element 185 that may be operable to, optionally,store an updated card number 129. The reissue application 127 hosts thesignal generation component 121. In examples, the reissue application127 upon execution by the mobile device processor 124 may cause themobile device processor 124 to be operable to cause the mobile devicedisplay 128 to present a user interface 126 that provides informationrelated to the payment card 110 including information that associatesthe payment card 110 with the reissue application 127 on the mobiledevice 120, and enables the reissue application respond to user inputsto the user interface 126.

In more detail, the reissue application 127 may enable a user to managea payment account, such as set authorized users, set spending limits,set and respond to purchase verification notifications, request areissue of the payment card number, or the like, maintained by thepayment account server 103 in the data storage 101. In an example, thereissue application 127 may be associated with the payment card 110 atthe authentication server 150. The reissue application 127 may, forexample, be provided by the service provider 105 and may be operable tolink to different services and servers, such as the application server106 and authentication server 150 as well as communicate with thepayment card 110. The reissue application may include a signalgeneration component 121, which generates signals, such as commandsignals, for output to other devices, such as the service provider 105,the payment card 110, or the like.

The mobile device 120 may include at least one input device (shown in alater example) coupled to a user interface 126 and a mobile devicedisplay 128. The mobile device 120 may further include a mobile devicedisplay 128, which may, for example, be a touchscreen display suitablefor providing the user interface 126, that is operable to displayinformation in response to signals generated by the reissue application127 executing on the mobile device 120 processor. The mobile devicedisplay 128 may be operable to display the user interface 126 thatpresents information in response to signals generated by the reissueapplication 127 executing on the mobile device 120 processor.

The mobile device processor 124, for example, may be operable to, viathe reissue application 127, present via the user interface 126 on themobile device display 128 a placement indication of where the paymentcard is to be placed with respect to the mobile device 120. Theplacement indication may indicate a placement of the payment card 110with reference to the mobile device 120 that enables near-fieldcommunication signals to be exchanged between the mobile devicenear-field communication device 125 and the payment card near-fieldcommunication device. The indicated placement may, for example, alignthe respective electrical fields of the respective near-fieldcommunication devices of the mobile device 120 and the payment card 110for near maximum signal strength. User preference display signalgeneration instructions may be information that is communicated betweenthe mobile device 120 and the payment card 110. The user preferencedisplay signal generation instructions may be generated by the signalgeneration component 121 into a signal, for example, based on theinformation related to the selected user preferences, and may be outputby the NFC device 125 as a user preference signal display to the paymentcard 110.

The signal generation component 121 may be hardware, software, firmwareor a combination thereof, that is operable to generate signals inresponse to instructions from the reissue application 127 executing onmobile device processor 124. For example, the signal generationcomponent 121 may be software that functions as part of the reissueapplication 127. In another example, the signal generation component 121may be a component of the mobile device 120 related, for example, to thetransceiver 187 or the mobile device processor 124, that is utilized bythe reissue application 127.

In some examples, the signal generation component 121 may be coupled to,or be part of, the mobile device processor 124. In an example, themobile device processor 124 may output user preference display signalgeneration instructions to the signal generation component 121. The userpreference display signal generation instructions may include userreference information that is to be output by the rewritable visualdisplay 113 of the payment card 110. The signal generation component 121may be operable to generate, according to the user preference displaysignal generation instructions, a user preference display signal. Theuser preference display signal, for example, may include the informationrelated to the selected at least one of the selectable user preferences.In an example, the signal generation component may include programmingcode that is executed by the mobile device processor 124 to process theuser preference display signal generation instructions for output as auser preference display signal. In an example, the signal generationcomponent 121 receive instructions from the mobile device processor 124to produce a signal for output to a payment card or another device, suchas the issuer server 108, or an entity, such as service provider 105. Inthe case where the instructions are to be sent to the issuer server 108or the service provider 105, the instructions may be output to arespective transceiver of the transceivers 187 for output by the mobiledevice 120 via the data network 130. The generated user preferencedisplay signal may be forwarded to the mobile device near-fieldcommunication device 125 for output from the mobile device 120.

In an example, the mobile device 120 may be operable to detect via themobile device near-field communication device 125, an authenticationsignal emitted from the payment card near-field communication device115. The authentication signal may be forwarded to the authenticationserver 150, and, in response to forwarding the authentication signal,the mobile device 120 may receive verification or authentication thatthe payment card 110 is a valid payment card having an authenticatedassociation with the mobile device 120. For example, as a result of theverification or authentication, the service provider has indicated thepayment card 110 is valid for use in transactions and that theassociation between the mobile device 120 and the payment card 110 isverified and authenticated.

The mobile device 120 may include a secure element 185. In someexamples, the mobile device processor 124, when obtaining the updatedcard number 129, may be operable to retrieve the updated card number 129from the secure element 185 of the mobile device. The mobile deviceprocessor 124 may report the updated card number of the payment card 110to an issuer server 108 that is related to an issuer of the paymentcard. In response to reporting the updated payment, the updated cardnumber may be deleted from the secure element 185 of the mobile device120.

The payment card 110 may be operable to receive, via the payment cardnear-field communication device 115, the user preference display signaloutput by the mobile device 120 near-field communication device. Theuser preference display signal may be processed by the microprocessor112 of the payment card 110. The processed user preference displaysignal may be forwarded to the display driver 633 and the rewriteablevisual display 113 for output of an updated card number. The paymentcard near-field communication device 115 may be operable to transformthe updated card number signal output by the mobile device NFC device125 to voltage values suitable to drive the rewriteable visual display113 (i.e., an electronic ink display in this example) to replace textand/or graphics, such as a card number, presented on the display withnew text and/or graphics, such as an updated card number. The paymentcard 110 may include a payment card near-field communication (NFC)device 125, a display driver 633, a rewriteable visual display 113, amicroprocessor 112, a counter 114, and a memory 116. The rewriteablevisual display 113 of the payment card 110 may be coupled to the displaydriver 633 may operable to present a card number. The rewriteable visualdisplay 113 may, for example, be an electronic ink display. The memory116 may store applet(s) 117 and other information 119. The applets 117may include an instance of the reissue application, such as reissueapplication 127, that may be obtained from the application server 106 ofthe service provider 105. In an example, the memory 116 may include asecure element (not shown) within the other information 119. In someexamples, the payment card processor 112 may be operable to retrieve anupdated card number 129 from the secure element. The counter 114 maykeep a count of the number of times the payment card 110 is used in atransaction or the like. The counter 114 count number may not be sharedoutside of the card, which makes the counter 114 count number difficultto determine by an eavesdropping device. Details of the applet(s) 117and other information 119 are explained in more detail with reference tothe examples of FIGS. 2-5.

The payment card 110 may be a contactless card that is in wirelesscommunication, for example, near-field communication (NFC), with themobile device 120. Via the NFC interaction between the payment card 110and the mobile device 120, the payment card 110 may harvest energy(described in more detail with reference to the example of FIG. 3B) fromthe mobile device's NFC signals to perform the functions as describedherein. For example, payment card 110 may comprise one or more chips,such as a radio frequency identification chip, operable to communicatevia NFC or other short-range protocols. In other examples, payment card110 may communicate with mobile device 120 through other meansincluding, but not limited to, Bluetooth, satellite, and/or Wi-Fi. Insome examples, the mobile device may be, for example, a card readerterminal, a cellular phone, a laptop, and/or a tablet. The payment card110 may be operable to communicate with the mobile device 120 throughNFC when the payment card 110 is within range of the respective mobiledevice. As described in more detail below, the payment card 110 mayinclude username, encryption key and counter information from counter114 that may be transformed using cryptographic algorithms to generate acryptogram including dynamic password that may be used by the serviceprovider to authenticate the mobile device.

The system 100 may also include an issuer server 108. The issuer server108 may be associated with an issuer (e.g., Mastercard, Visa, AmericanExpress, Discover, or the like) of the payment card 110. The issuerserver 108 may be coupled to the data network 130 and be communicativelycoupled to communicate with the service provider 105 and the mobiledevice 120. The issuer server 108 and components of the service provider105 may cooperate with one another to provide services to the mobiledevice 120. In some examples, the issuer server 108 may store theupdated card number 129. The mobile device processor 124 via the reissueapplication (app) 127 may enable the mobile device 120 to retrieve theupdated card number from the issuer server 108.

Details of an operation example are described in more detail withreference to the examples of FIGS. 4 and 5. However, it may bebeneficial at this time to briefly describe an operational example thatexplains the interaction of the respective components of the system 100with reference to FIG. 1. In the example, the mobile device 120 may beoperable to send, by the reissue application 127, a request to theauthentication server 150 sent via the data network 130. The request maybe made to the authentication server 150 to verify that the mobiledevice 120 is associated with the payment card 110. In response to averification that the mobile device 120 is associated with the paymentcard 110, the mobile device 120 may obtain an updated card number (CN)129. As shown, the updated card number may be stored in a number ofdifferent locations within the system 100. For example, the updated cardnumber 129 may be stored in a secure location by the service provider105 in a payment account server that is coupled to a data storage device101. In an example, the updated card number 129 may be stored withpayment account information 102. The payment account information 102 mayinclude information related to each payment card account managed andserviced by the service provider 105. Alternatively, the issuer server108 may store a number of unused or unassigned payment card numbers thatmay be used as an updated card number 129.

In the example, the updated card number 129 is different from a cardnumber displayed on the payment card 110 prior to issuing an updatedcard number. The signal generation component 121 may be operable togenerate an updated card number signal. The updated card number signalmay, for example, include the updated card number and other relatedinformation, such as an encryption key, authorized user name(s), a cardverification value, an expiration date, an issuer name, or the like. Inanother example, the updated card number signal may be a signal withoutthe updated card number that instead indicates that the updated cardnumber is to be generated by a device, such as payment card, an issuerserver, or the like, that receives the updated card number signal. In afurther example, a card verification value may be another identifier,such as a hash value or the like, related to the payment card 110 thatmay be used by, for example, the authentication server 150 to further toconfirm or verify that the payment card 110 is authentic, valid or isassociated with a user who also possesses the mobile device 120. Theupdated card number signal may be output via the mobile devicenear-field communication device 125. In the example, the payment card110 may be operable to receive, via a payment card near-fieldcommunication device 115, the updated card number signal output by themobile device near-field communication device 125. In response toreceiving the updated card number signal, the microprocessor 112 may beoperable to process the updated card number signal, and, based on theupdated card number signal, the rewriteable visual display 113 may bedriven (by display driver 633) to present the updated card numberinstead of the displayed card number.

The payment card 110 may include a number of components, such as thoseshown in FIG. 1, but a more detailed discussion of an example of apayment card is provided with reference to FIGS. 2 and 3A-B.

FIG. 2 provides a front view of an example of a payment card 200suitable for use in the example processes described herein. The paymentcard 200 may be operable as a payment card, such as a credit card, debitcard, or gift card, issued by a service provider/issuer, whose name 205is displayed on the front (or the back, in some examples) of the paymentcard 200. The contactless, payment card 200 may also include useridentification information 215 displayed on the front and/or back of thepayment card 200, a rewriteable visual display 207, and a contact pad220 as well as the service provider/issuer name 205.

The payment card 200 may include a substrate 210, which may include asingle layer, or one or more laminated layers composed of plastics,metals, and other materials. Examples of materials that may be used toform the substrate 210 include polyvinyl chloride, polyvinyl chlorideacetate, acrylonitrile butadiene styrene, polycarbonate, polyesters,anodized titanium, palladium, gold, carbon, paper, biodegradablematerials, and or the like. In some examples, the payment card 200 mayhave physical characteristics compliant with the ID-1 format of theISO/IEC 7810 standard, and the payment card 200 may otherwise becompliant with the ISO/IEC 14443 standard. However, it is understoodthat the payment card 200 according to the present disclosure may havedifferent characteristics.

The rewriteable visual display 207 may be an electronic ink display thatresponds to drive signals to set the state of the display, and inresponse to the drive signals being removed the electronic ink displayremains static in the state set by the last applied drive signal. Forexample, an example of a currently-displayed or prior-assigned paymentcard number may be “1234 5678 1234 5678” as shown in the rewriteablevisual display 207. The payment card 200 may also include a magneticstrip or tape, which may be located on the back of the card (not shown).As described in the following examples, the currently-displayed orprior-assigned payment card number “1234 5678 1234 5678” may be writtenover with an updated card number such as “0987 6543 2109 8765” or thelike. As a result, the payment card with the updated card number may bereissued and used in future transactions.

In an example, the payment card 200 may include a rewriteable magneticstrip that is rewritten with the updated card number at substantiallythe same time that the updated card number is provided to the electronicink display for use in future transactions.

The payment card 200 may also include user identification information215 displayed on the front and/or back of the card, and a contact pad220. The user identification information 215 (shown as “CardholderName”) may be a user's name or nickname. The contact pad 220 may beoperable to establish contact with another communication device, such asa mobile device, a smart phone, a laptop, a desktop, a tablet computer,or the like. The payment card 200 may also include processing circuitry,antenna and other components shown in other examples. These componentsmay be located behind the contact pad 220 or elsewhere on the substrate210.

As explained above, the payment card 200 may be built on a softwareplatform operable on smart cards or other devices that comprises programcode, processing capability and memory, such as JavaCard. In someexamples, applets, such as 117 of FIG. 1, may be added to contactlesspayment cards to generate requests to reissue card numbers as well asother services, such as issuing a one-time password (OTP) formultifactor authentication (MFA) in various mobile application-based usecases. Thus, the functionality of the contactless payment card enablescommunication with a mobile device to reissue a payment card number asdescribed below with reference to FIGS. 3A-5.

FIG. 3A is a block diagram illustrating examples of components of thecontactless payment card of FIG. 2 in more detail.

As illustrated in FIG. 3A, underneath (and coupled to) the contact pad320 may be processing circuitry 325 for processing and storinginformation and one or more antennas 355. In addition to a logic circuitand the like, it is understood that the processing circuitry 325 may,for example, contain additional components, including processors,memories, error and parity/CRC checkers, data encoders, anti-collisionalgorithms, controllers, command decoders, security primitives,tamper-proofing hardware, or the like as necessary to perform thefunctions described herein.

The one or more antennas 355 may be placed within the payment card andunder contact pad 320 and around the processing circuitry of the contactpad 320. For example, the one or more antennas 355 may be integral withthe processing circuitry 325, while another of the one or more antennasmay be used with an external booster coil. In another example, the oneor more antennas 355 may be external to the contact pad 320 and theprocessing circuitry. The one or more antennas 355 may also provideinductance needed to harvest power to drive, for example, the processingcircuitry 325, the memory 335, the rewriteable visual display 207 ofFIG. 2, and the like. The processing circuitry 325 may include a powermanagement unit (not shown) which may be operable to manage the powersupply and storage for the payment card 200.

In an example of energy harvesting, FIG. 3B illustrates an example of anapparatus 360 that supplies power to a payment card for modifying arewriteable visual display of a payment card example as described withreference to FIGS. 2 and 3A-B. In the example apparatus 360 of FIG. 3B,the antenna 362 may be an NFC compatible antenna configured to receiveNFC signals. In the example of FIG. 3B, the antenna 362 may be operableto provide both communications and the inductance needed for powerharvesting. As mentioned above, the antenna 362 may be coupled to acommunication interface (shown in the example of FIG. 3A) that providesthe signal to processing circuitry for signal processing (as describedwith reference to FIG. 3A). For example, the power captured by theantenna 362 may, for example, be obtained from a 13.56 MHz NFC signalthat generates an alternating current within the antenna 362. Of course,radio frequency signals of a frequency different than 13.56 MHz may alsobe used. The matching circuit 363 may be a part of the antenna 362 thatis matched to the incoming magnetic field to produce maximum inductance.In the example, the inductive-capacitive (LC) filter 364 may act as alow pass filter, which removes high-frequency components from thereceived signal that are unnecessary for communication. Thecommunication output by processing circuitry (shown in FIG. 3A).

The energy from the induced electrical current and induced voltage isharvested by the energy harvesting component 361. The induced voltagemay be approximately around 0.1 volts (V). The voltage may be providedto the power management unit 365 for rectification, smoothing and otherprocessing as well as distribution to other components, such as displaydriver 333 or NFC circuitry 368 that may be controlled by amicroprocessor (shown in other examples). In the example, the inducedvoltage may power the changes on a rewriteable visual display, such asan e-ink display. If the induced voltage is too low, it may be increasedusing additional circuit elements and technique such as using atransformer with a greater number of turns of the coil or an increasedpermanent magnetic field. When the payment card is not being reissuedsince the e-ink display only needs to be powered when being changed, thepayment card may harvest energy while being used with NFC devices andstore the harvested energy in an energy storage device 367, which may bea battery, a capacitor, a supercapacitor or the like, to store power fora future change of the display. The power management unit 365 may, in afurther example, include an intermediate energy storage device, such asa capacitor to smooth out the voltage provided by the energy harvestingcomponent 361.

In the examples, signals received via the NFC antenna 362 may be used topower the NFC circuitry 368 directly or the power can be captured viathe energy harvesting component 361 to drive the display driver 333,under control of a processor, to update the payment card number andpresent other information via changes to an e-ink display as describedwith reference to other examples.

Returning to the example of FIG. 3A, the memory 335 may be a read-onlymemory, write-once read-multiple memory or read/write memory, e.g., RAM,ROM, and EEPROM, and the processing circuitry 325 may include one ormore of these memories. For example, a read-only memory may be factoryprogrammable as read-only or one-time programmable. One-timeprogrammability provides the opportunity to write once then read manytimes. A write once/read-multiple memory may be programmed at a point intime after the memory chip has left the factory. Once the memory isprogrammed, it may not be rewritten, but it may be read many times. Aread/write memory may be programmed and re-programmed many times afterleaving the factory. It may also be read many times.

The memory 335 may be operable to store one or more applets 340, one ormore counters 345, and payment card account identifier(s) 350. The oneor more applet(s) 340, one or more counters 345, and a payment cardaccount identifier 350. The one or more applet(s) 340 may comprise oneor more software applications associated with a respective one or moreservice provider applications (provided, for example, by serviceprovider 105 of FIG. 1) and operable to execute on one or more paymentcards, such as a Java Card applet. For example, an applet of applet(s)340 may be operable to respond to one or more requests, such asnear-field data exchange (NDEF) requests, from a reader, such as a NearField Communication (NFC) reader and produce an NDEF message thatcomprises a cryptographically secure OTP encoded as an NDEF text tag.According to an example, each applet may store a username for a userassociated with the payment card account to access the associatedservice provider application. The one or more counters 345 may comprisea numeric counter sufficient to store an integer that, in some examples,is representative of the number of times the payment card 200 is used.

The payment card account identifier(s) 350 may comprise a uniquealphanumeric identifier assigned to a user of the payment card 200and/or one or more encryption keys that together may be used todistinguish the user of the payment card from other payment card users.In some examples, the payment card account identifier(s) 350 may includeinformation identifying both a customer and an account assigned to thatcustomer and may further identify the payment card associated with thecustomer's account. According to some aspects, the username 342 may bederived from a combination of the one or more of the payment cardaccount identifier(s) 350 and/or one or more encryption keys 343.

For example, with reference to FIGS. 1 and 3, the memory 335 may includeusername 342, an encryption key 343 and counter 345 information that maybe transformed by the microprocessor 330 using, for example,cryptographic algorithms to generate an encryption key including adynamic password that may be used by the service provider'sauthentication server 150 of FIG. 1 to authenticate the payment card110, the mobile device 120, a user (not shown), or all three. Forexample, the microprocessor 330 may use the payment card accountidentifier(s) 350, the encryption key 343, and a value from one of thecounter 345, in cryptographic processing functionality provided by themicroprocessor 330 to generate an encryption key including a dynamicpassword that may be used, together with the username, to authenticate areissuing of payment card 110 and the provision of an updated cardnumber 129 to the payment card 110 via the mobile device 120. In oneexample, the dynamic password relates to the counter 345. In such anexample, the dynamic password thus advantageously reflects previousbehaviors of the holder of the payment card 110. For example, thecounter-based dynamic password may reflect the number of times that theuser has used the payment card 110 to obtain a particular service (e.g.,money advance, transaction authorization, or the like) of the serviceprovider 105, which is a knowledge factor that is virtually impossiblefor a malicious third party to ascertain. For example, the number oftimes the payment card 110 is used may be stored as the counter 345value in a secure memory of the payment card and the counter value maybe incremented each time the payment card is used in a transaction.

The microprocessor 330 and memory 335 elements of the foregoingexemplary examples are described with reference to the contact pad 320,but the present disclosure is not limited thereto. It is understood thatthese elements may be implemented outside of the contact pad 320 orentirely separate from it, or as further elements in addition tomicroprocessor 330 and memory 335 elements located within the contactpad 320.

Returning to FIGS. 2 and 3A-B, in some examples, the payment card 200may comprise one or more antennas 355 placed around the processingcircuitry 325 of the contact pad 320. For example, the one or moreantennas may be integral with the processing circuitry 325 and the oneor more antennas 355 may be used with an external booster coil. Asanother example, the one or more antennas 355 may be external to thecontact pad 320 and the processing circuitry 325. In an example, the oneor more antennas 355 may extend around the area of the card to increasethe power transfer characteristics of the antenna when placed in anelectric field, such as an NFC field of a mobile device.

The processing circuitry 325 may include one or more communicationsinterface(s) 337, such as a radio frequency identification (RFID) chip338, coupled to the one or more antennas 355 operable to communicatewith a mobile device, such as 120 of FIG. 1, via one or more short-rangewireless communication protocols such as near-field communication (NFC),the Europay, Mastercard, Visa (EMV) standard, or the like, and inconformance with ISO/IEC 14443. In some examples, the RFID chip 338 mayalso be referred to as a payment card near-field communication device,such as 115 of FIG. 1. Although NFC is used as an example communicationsprotocol, the disclosure is equally applicable to other types ofwireless communications, such as the EMV standard, Bluetooth, and/orWi-Fi. The RFID chip 338 may include additional components, such asthose shown in the example of FIG. 3A.

The payment card account identifier(s) 350 may comprise a uniquealphanumeric identifier assigned to a user of the payment card 200and/or one or more encryption keys 343 that together may be used todistinguish the user of the payment card from other payment card users.In some examples, the payment card account identifier(s) 350 may includeinformation identifying both a customer and an account assigned to thatcustomer and may further identify the payment card (i.e., payment cardnumber) associated with the customer's account. According to someaspects, the username 342 may be derived from a combination of the oneor more of the payment card account identifier(s) 350 and/or one or moreencryption keys 343.

In an example, the reissue of a payment card number may utilize, apassword-less authentication protocol that practically applies acontactless, payment card cryptogram exchange protocol as a first factorauthentication mechanism to facilitate application service accesswithout sacrificing application service security.

The payment card cryptogram exchange protocol includes registering apayment card of a client with an application service, binding thecontactless card to the client and using a cryptogram exchange protocolto perform first factor, second factor and/or other authentication ofclient access requests by utilizing one of the applet(s) 340, a countervalue from counter 345, a key value from encryption key 343, and themicroprocessor 330.

In order to insure valid authentication of a payment account, the mobiledevice and the payment card, the three are typically bound to oneanother by associating digital credentials of the payment account, themobile device and the payment card with one another.

For example, the payment card may be registered with the serviceprovider 105 to receive a reissue application service. As part of theregistration, a username, such as 342, may be is stored in the datastorage device 109 coupled to the authentication server 150. In someexamples, the username may be automatically generated by the serviceprovider 105, unknown to the mobile device, and loaded into both a userinformation table (not shown) stored in the data storage device 109 andan applet of applet(s) 340 downloaded on the payment card 110. As anexample, the payment card is associated with a user and a user's paymentaccount which is maintained by the payment account server 103 and storedin data storage device 101. A payment card number (e.g., 1234 5678 12345678), user information and user payment account information (i.e., anaccount number or other identifier) may be maintained and stored by theservice provider 105 via the payment account server 103. The paymentaccount information 102 also includes information regarding a mobiledevice associated with the user, the payment card, and the user paymentaccount. For example, the payment account information 102 may includemobile device 120 information such as a unique identifier associatedwith the mobile device (e.g., a telephone number, a mobile equipmentidentifier (MEID), an international mobile equipment identity (IMEI), aninternational mobile subscriber identity (IMSI), a serial number, amedia access control (MAC) address, and/or the like), applicationinformation related to an application that was used to capture the image(e.g., an identifier of an instance of the application, an applicationversion of the application, and/or the like), and/or the like. Once thepayment card is registered with the service provider 105 and bound tothe mobile device, application authentication using a payment cardcryptographic algorithm may be performed to enable authentication of thepayment card, the mobile device and the user, which enables reissue ofthe payment card via the reissue application. Examples of acryptographic algorithm suitable for use with the disclosed examplesinclude 3DES (Triple Data Encryption Algorithm), Advanced EncryptionStandard (AES); a symmetric Hash Based Message Authentication (HMAC)algorithm, such as HMAC-SHA-256; and a symmetric cypher-based messageauthentication code (CMAC) algorithm such as AES-CMAC, or the like. Thislevel of security enables the following process to be executed securely,thereby mitigating concern by a service provider or payment account userof an unscrupulous person fraudulently compromising a payment card suchas that as described herein.

FIG. 4 is a flow chart of an example process performed by a mobiledevice using in a system such as that illustrated in FIG. 1. In anexample, an e-ink display-enabled card has been compromised (e.g.,fraudulent transactions have been made using the payment card number)and the payment card needs to be reissued. Instead of replacing thepayment card (110 of FIG. 1 or 200 of FIG. 2), the payment card in thedisclosed examples may have the number on the payment card to bechanged. In the example, the payment card may be placed within anelectric field of the NFC device a mobile phone (e.g. “tapped to phone”)and provide information to authenticate the payment card. Based onauthentication of the card and the mobile device, the mobile device isoperable to pass over the new information: card number, cardverification value (CVV), expiration date, service provider/issuer(e.g., VISA or MASTERCARD), all of or some of which may be displayed.For example, the e-ink display is modified, and when the payment card isremoved from the NFC field of the mobile device, the e-ink display isheld static.

In more detail, the process 400 may include the mobile device sending arequest to update a card number on a payment card to be reissued (410).The request may include an indication that a card number presented onthe display of the payment card and/or encoded on a magnetic strip ofthe payment card is invalid and unusable to complete a transaction(e.g., a purchase of an item or service, or the like). A payment cardnumber may become invalid and unusable because the payment card numberhas been compromised by identity theft, user carelessness or the like.In some examples, prior to sending the request for authorization toreissue the payment card, an authentication message may be generated bya reissue application, such as 127 of FIG. 1, executing on the mobiledevice. The authentication message may, for example, include informationrelated to the mobile device stored by an authentication server of aservice provider. The authentication message may be included in therequest with the indication.

In response to the sent request, the mobile device 120 may receive anauthorization to reissue the payment card and update the card number(420). For example, the mobile device 120 may receive authorization toreissue the payment card and update the card number based on anauthentication message included in the request. For example, theauthentication message included in the request may have information,such as the encrypted messages, that is processed by the authenticationserver 150. An authentication status message may be sent fromauthentication server 150 to the payment account server 103, theapplication server 106 or both. In response to the authentication statusmessage, the payment account server 103 or the application server 106may obtain and send the updated card number and/or informationassociated with the selected user preferences (described in more detailbelow).

In this example, the card number encoded on a magnetic strip of thepayment card may not be updated. In response to the receivedauthorization, an updated card number may be obtained from a securesource of updated card numbers (430). In the example, the mobile devicemay obtain the updated card number by retrieving the updated card numberfrom a secure element of the mobile device. Upon retrieving the updatedcard number from the secure element, the mobile device may report theupdated card number of the payment card to, for example, an issuerserver related to an issuer of the payment card, or a financialinstitution related to the payment card or the like. The mobile devicemay delete the updated card number from the secure element or take someother action to insure the updated card number is not inadvertentlyreused again. As shown in FIG. 1, the updated card number (CN) 129 maybe stored in various locations and may be obtained by the mobile device120 upon request and authorization by a respective source. For example,the secure source of the updated card numbers may, for example, be oneor more a number of various sources, such as a secure element within amobile device, a secure element within the payment card, a source withinthe service provider, a source within an issuer of the payment card, oranother secure source. Instead of obtaining an updated card number ofthe secure element of the mobile device, the mobile device, whenobtaining the updated card number from a secure source of updated cardnumbers, may retrieve the updated card number from an issuer serverassociated with an issuer of the payment card, such as an issuer serversuch as 108 in FIG. 1. In other examples, updated card numbers may begenerated by a reissue application 127 of the mobile device using acryptographic hash function based on data retrieved from the paymentcard 110 of FIG. 1. In another example, the processor 112 of the paymentcard 110 may be operable to generate an updated card number, forexample, by using a cryptographic hash function or some other functionand data maintained in the payment card memory, such as data fromcounter 114 or the like. In the example, the cryptographic hash functionor other function may be secure sources of updated card numbers by usingvarious cryptographic and other security techniques. When the paymentcard 110 of FIG. 1 generates the updated card number, the authenticationserver 150 of FIG. 1 may be used to authenticate the payment card 110via the mobile device 120. Once authenticated, the payment card 110itself may generate the updated card number.

In yet another example, at step 430, the mobile device 120 whenobtaining the updated card number from the secure source of updated cardnumbers, may retrieve the updated card number from a secure element ofthe mobile device. The mobile device 120 may report the updated cardnumber of the payment card to an issuer server related to an issuer ofthe payment card and delete the updated card number from the secureelement.

In response to command signals from a signal generation componentexecuting on the mobile device, an updated card number signalrepresenting the updated card number may be output via a near-fieldcommunication circuit or device in the mobile device (440). With thepayment card being within range of the near-field communication circuitor device in the mobile device, the near-field communication deviceembedded in the payment card to be reissued may receive the updated cardnumber signal (450). In an example, the payment card may also receive anauthentication signal from the mobile device 120 via the payment cardnear-field communication device. The logic circuit on the payment devicemay verify, for example, utilizing an encryption key or the like, thatthe mobile device 120 is associated with the payment card.

The payment card may use the energy from the updated card number signalto supply power to a microprocessor to respond to the received signals.For example, at 460, in response to receiving the updated card numbersignal and harvesting energy from the received signal, a visual displayon the payment card may be modified to indicate the updated card number.In an example of a payment card equipped with a rewriteable magneticstrip, the payment card microprocessor may be operable to rewrite therewriteable magnetic strip with the updated card number. Conversely, inan example of when a payment card is not equipped with a rewriteablemagnetic strip, the updated card number is different from the cardnumber represented by the magnetic strip of the payment card to bereissued. In addition, the updated card number signal may include avalue that indicates that the magnetic strip is invalid and unusable topoint of sale devices that continue to use swipe technology. The paymentcard may store the value that indicates that the magnetic strip isinvalid and unusable and provide information related to the value to thepoint of sale device. Alternatively, the updated card number itself mayindicate the magnetic strip is invalid or the authentication server mayhave a setting that provides the indication to the point of sale devicethat the magnetic strip is invalid and unusable.

In another example, the updated card number may be a temporary paymentcard number, such as a temporary virtual number, usable for a singletransaction, a predetermined time period, or the like. The temporaryvirtual number may be displayed for a limited time such as for theduration of the single transaction, the predetermined time period or thelike. In another example, the rewriteable visual display may be used todisplay one-time use “tokens,” the temporary virtual numbers, or dynamiccredit card numbers. These would be provisioned by either theapplication server or authentication server and transmitted to thepayment card via NFC of a mobile device or the like. The display maypresent indication that the token, temporary virtual number or dynamiccredit card number is not a primary payment account number.

In some examples, the process 400 may include enable the mobile deviceto perform additional functions. These additional functions, forexample, increase user awareness of the monetary value associated withtheir payment card by providing additional information that may be timeconsuming and inconvenient to obtain. For example, in response to a userinput, the mobile device may select account display preferences fordisplaying information on payment card. In response to the selectedaccount display preferences, a signal generation component of the mobiledevice may modify signal parameters for rewriting the rewriteable visualdisplay according to the selected account display preferences. Themodified signal parameters may be used to transmit a user preferencedisplay signal to the payment card. The transmitted user preferencedisplay signal causes a presentation of information on the visualdisplay of the payment card, such as one or more of: a last transactionamount, a rewards total amount, an account balance, an account ceilinglimit, or a warning related to account balance. Of course, otherinformation may be provided. The presented information may be obtainedfrom the service provider 105, for example, from the payment accountserver 103, the application server 106 or the like.

A payment card, such as 110 of FIG. 1, may be operable to execute aprocess for authentication of the card in order to receive the updatedcard number. FIG. 5 is a flow chart illustrating an example of a process500 executed by the payment card of the system example of FIG. 1. In theexample, at 510, a processor of the payment card may generate anauthentication signal that includes a payment card number currentlydisplayed on a visual display of the payment card. In the example, anear-field communication device of the payment card may emit thegenerated authentication signal for receipt by a near-fieldcommunication device of a mobile device. In the example, the emittedauthentication signal may include a payment card number currentlydisplayed on the payment card. The emitted authentication signal may beemitted after the payment card is introduced into any portion of anear-field communication electric field surrounding the mobile device.The emitted authentication signal may be an approval of a request tochange, or reissue, the card number currently displayed on a visualdisplay of the payment card. In the example, the payment card may storein a memory device within the payment card an indication that a cardnumber encoded on a magnetic strip of the payment card is invalid andunusable.

While the payment card remains within any portion of the near-fieldcommunication electric field surrounding the mobile device, a near-fieldcommunication device of the payment card may receive an updated cardnumber signal (520). In one example, the updated card number signal maybe received from the mobile device and may contain only an updated cardnumber. In other examples, the updated card number signal received fromthe mobile device may contain the updated card number as well as otherinformation, such as information based on user selected preferences.

In a specific example, the updated card number signal may be related toa provisioning of an Europay, Mastercard, Visa (EMV) profile. In anexample, EMV profiles contain authentication keys used to verifytransactions with chip-based and contactless payment transactions. Theseauthentication keys can be encrypted and sent with the card's symmetricmaster key (stored in the cards secure memory, such as a secure element)or done through activating backup “profiles.” The backup profiles may,for example, be inactive full sets of EMV compliant-data on the chip ofa payment card that become primary payment card numbers (i.e., paymentcard numbers that are authorized for use in transactions). On activationof a respective updated payment card number, the payment card maydisplay the updated payment card number as a new primary account number(PAN).

In response to receiving the updated card number signal, the card numbercurrently displayed on the visual display of the payment card may bereplaced with the updated card number (530). For example, a processor orlogic circuit on the payment card may, in response to receiving theupdated card number signal by the near-field communication device of thepayment card, generate a display drive signal for driving the visualdisplay of the payment card to change the card number currentlydisplayed.

The payment card may also receive, at 540, an account status signal maybe received via the near-field communication device of the mobiledevice. In response to the account status signal, the visual display ofthe payment card may be modified to present at least one of: a paymentcard account balance, a most recent transaction amount, an annualpercentage rate of account, a rewards points balance, a payment duedate, a location-based discount, or a location-based reward.

The process 500 may further include selecting account displaypreferences for modifying information displayed on payment card. Forexample, the signal generation component under control of the reissueapplication 127 may modify signal parameters in response to the selectedaccount display preferences. Prior to transmitting the signalrepresenting the updated card number, a display preference signal thatis based on the selected preferences may be transmitted to the paymentcard. The display preference signal may cause the display on paymentcard e-ink display of one or more of: a last transaction amount, arewards total amount, an account balance, an account ceiling limit, or awarning related to account balance.

In other examples, the user preference display signal, in addition tothe updated card number, may include information related to the selectedat least one of the selectable user preferences. For example, the mobiledevice processor 124 of FIG. 1 may be operable, via a user interfaceprovided by execution of the reissue application 127, to present a menuof selectable user preferences on the mobile device display 128.

In the example, the selectable user preferences in the menu may includeone or more of: a payment card account balance, a most recenttransaction amount, an annual percentage rate of account, a rewardspoints balance, a payment due date, a location-based discount, or alocation-based reward. Through at least one input device (such as atouchscreen, button, keypad or the like), a selection of at least one ofthe selectable user preferences may be received by the mobile device120. The at least one selected user preference may be stored in thememory. In an example, each selected user preference may be presented onthe rewriteable visual display 113 of payment card 110 whenever thepayment card 110 and the mobile device 120 communicate with one another,regardless of whether a payment card number is going to be reissued. Themobile device processor 124 may be further operable to, via the reissueapplication 127, obtain information related to the selected at least oneof the selectable user preferences in response to a verification thatthe mobile device 120 is associated with the payment card 110. Theinformation related to the selected at least one of the selectable userpreferences may be stored in the memory 122, for example, in otherelements 189, or retrieved via the authentication server 150, paymentaccount server 103 or application server 106. The memory 122 may also beoperable to store user-related numbers, information related to usersauthorized to use the payment card, or the like.

In another example, the payment account server 103 may be operable toretrieve the updated card number from the data storage device 101 inresponse to a request from the mobile device 120. The payment accountserver 103 may send the updated card number to the reissue application127 executing on the mobile device.

In response to the account status signal, the visual display of thepayment card may be modified to present at least one of: a payment cardaccount balance, a most recent transaction amount, an annual percentagerate of account, a rewards points balance, a payment due date, alocation-based discount, or a location-based reward (550). In someexamples, prior transaction information may be stored in a memory, suchas 335 of FIG. 3A. When the payment card is placed in a near-fieldcommunication electrical field, the payment card may harvest energy topresent a portion of the prior transaction information.

In another example, the rewriteable visual display may be used todisplay one-time use “tokens” or dynamic credit card numbers. Thesewould be provisioned by the server and transmitted to the card via NFC.There would probably be some sort of indication that it isn't theprimary account number.

In addition to reissuing payment card numbers for use in futuretransactions, the rewriteable visual display may be controlled to changethe type of card. For example, a payment card may be completely changedinto another kind of card, such as a prescription card, an identitycard, a debit card or the like. Of course, to provide such as change inthe type of card, the service provider, such as 105 of FIG. 1, may haveaccess to, or provide, the respective services related to a prescriptioncard, an identity card, a debit card or the like.

FIG. 6 illustrates an example of a computing architecture 600 suitablefor implementing various examples as previously described. In oneexample, the computing architecture 600 may be incorporate elements asmay be typically used to implement a server or network platform, ifappropriately programmed, as part of system 100. In another example, thecomputing architecture 600 may be incorporate optional elements that maybe typically used to implement a smart digital device or a computingdevice that may be implemented as part of system 100.

The computing architecture 600 includes various common computingelements, such as one or more processors, multi-core processors,co-processors, memory units, chipsets, controllers, peripherals,interfaces, oscillators, timing devices, video cards, audio cards,multimedia input/output (I/O) components, power supplies, and so forth.The examples, however, are not limited to implementation by thecomputing architecture 600.

As shown in FIG. 6, the computing architecture 600 includes a processingunit 604, a system memory 606 and a system bus 608. The processing unit604 can be any of various commercially available processors or number ofprocessors.

The system bus 608 provides an interface for system componentsincluding, but not limited to, the system memory 606 to the processingunit 604. The system bus 608 can be any of several types of busstructures that may further interconnect to a memory bus (with orwithout a memory controller), a peripheral bus, and a local bus usingany of a variety of commercially available bus architectures. Interfaceadapters may connect to the system bus 608 via slot architecture.Example slot architectures may include without limitation AcceleratedGraphics Port (AGP), Card Bus, (Extended) Industry Standard Architecture((E)ISA), Micro Channel Architecture (MCA), NuBus, Peripheral ComponentInterconnect (Extended) (PCI(X)), PCI Express, Personal Computer MemoryCard International Association (PCMCIA), and the like.

The computing architecture 600 may include or implement various articlesof manufacture. An article of manufacture may include acomputer-readable storage medium to store logic. Examples of acomputer-readable storage medium may include any tangible media capableof storing electronic data, including volatile memory or non-volatilememory, removable or non-removable memory, erasable or non-erasablememory, writeable or re-writeable memory, and so forth. Examples oflogic may include executable computer program instructions implementedusing any suitable type of code, such as source code, compiled code,interpreted code, executable code, static code, dynamic code,object-oriented code, visual code, and the like. Examples may also be atleast partly implemented as instructions contained in or on anon-transitory computer-readable medium, embodied with programming codethat may be read and executed by one or more processors to enableperformance of the examples of operations described herein.

The system memory 606 may include various types of computer-readablestorage media in the form of one or more higher speed memory units, suchas read-only memory (ROM), random-access memory (RAM), dynamic RAM(DRAM), Double-Data-Rate DRAM (DDRAM), synchronous DRAM (SDRAM), staticRAM (SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM),electrically erasable programmable ROM (EEPROM), flash memory, polymermemory such as ferroelectric polymer memory, ovonic memory, phase changeor ferroelectric memory, silicon-oxide-nitride-oxide-silicon (SONOS)memory, magnetic or optical cards, an array of devices such as RedundantArray of Independent Disks (RAID) drives, solid state memory devices(e.g., USB memory, solid state drives (SSD) and any other type ofstorage media suitable for storing information. In the illustratedexample shown in FIG. 6, the system memory 606 can include non-volatilememory 610 and/or volatile memory 612. A basic input/output system(BIOS) can be stored in the non-volatile memory 610.

The computer 602 may include various types of computer-readable storagemedia in the form of one or more lower speed memory units, including aninternal hard disk drive (HDD) 614 (or, optionally, external hard diskdrive (HDD) 613), a magnetic floppy disk drive (FDD) 616 to read from orwrite to a removable magnetic disk 618, and an optical disk drive 620 toread from or write to a removable optical disk 622 (e.g., a CD-ROM orDVD). The HDD 614 or 613, FDD 616 and optical disk drive 620 can beconnected to the system bus 608 by an HDD interface 624, an FDDinterface 626 and an optical drive interface 628, respectively. The HDDinterface 624 for external drive implementations can include at leastone or both of Universal Serial Bus (USB) and IEEE 1394 interfacetechnologies.

The drives and associated computer-readable media provide volatileand/or nonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For example, a number of computer programmodules can be stored in the drives and memory 610, 612, including anoperating system 630, one or more application programs 632, otherprogram modules 634, and program data 636. In one example, the one ormore application programs 632, other program modules 634, and programdata 636 can include, for example, the various applications and/orcomponents of the computing architecture 600. At least onecomputer-readable storage medium may include instructions that, whenexecuted, cause a system to perform any of the computer-implementedmethods and processes described herein.

Optionally, when configured as a mobile device, a smart digital device,a laptop or the like, the computing architecture 600 may includeadditional devices to enable data input and output to a user. Forexample, a user may enter commands and information into the computer 602through one or more wire/wireless optional input devices, for example, akeypad 638 and a tactile input device, such as a touchscreen 640. Otherinput devices may include microphones, infra-red (IR) remote controls,radio-frequency (RF) remote controls, game pads, stylus pens, near-fieldcommunication devices, dongles, finger print readers, gloves, graphicstablets, joysticks, keyboards, retina readers, touch screens (e.g.,capacitive, resistive, etc.), trackballs, track pads, sensors, styluses,and the like. These and other input devices are often connected to theprocessing unit 604 through optional interface 642 that is coupled tothe system bus 608 but can be connected by other interfaces such as aparallel port, IEEE 1394 serial port, a game port, a USB port, an IRinterface, and so forth.

Another optionally element may be display 644, which may be an organiclight emitting diode (OLED), light emitting display (LED), or other typeof display device, that is also connected to the system bus 608 via aninterface, such as an optional video adaptor 646. The display 644 may beinternal or external to the computer 602. In addition to the display644, a computer typically includes other peripheral output devices, suchas speakers, printers, and so forth which may be coupled to the systembus 608 via the optional interface 642.

The computer 602 may operate in a networked environment using logicalconnections via wire and/or wireless communications to one or moreremote computers, such as a remote computer 648. The remote computer 648can be a workstation, a server computer, a router, a personal computer,portable computer, microprocessor-based entertainment appliance, a peerdevice or other common network node, and typically includes many or allthe elements described relative to the computer 602, although, forpurposes of brevity, only a remote memory/storage device 659 isillustrated. The logical connections depicted include wire/wirelessconnectivity to a local area network (LAN) 652 and/or larger networks,for example, a wide area network (WAN) 654. Such LAN and WAN networkingenvironments are commonplace in offices and companies, and facilitateenterprise-wide computer networks, such as intranets, all of which mayconnect to a global communications network, for example, the Internet.

When used in a LAN networking environment, the computer 602 may beconnected to the LAN 652 through a wire and/or wireless communicationnetwork interface or adaptor 656. The adaptor 656 can facilitate wireand/or wireless communications to the LAN 652, which may also include awireless access point disposed thereon for communicating with thewireless functionality of the adaptor 656.

When used in a WAN networking environment, the computer 602 can includea modem 658, or is connected to a communications server on the WAN 654or has other means for establishing communications over the WAN 654,such as by way of the Internet. The modem 658, which can be internal orexternal and a wire and/or wireless device, connects to the system bus608 via the interface 642. In a networked environment, program modulesdepicted relative to the computer 602, or portions thereof, can bestored in the remote memory/storage device 659. It will be appreciatedthat the network connections shown are exemplary and other means ofestablishing a communications link between the computers can be used.

The computer 602 is operable to communicate with wired and wirelessdevices or entities using the IEEE 802 family of standards, such aswireless devices operatively disposed in wireless communication (e.g.,IEEE 802.11 over-the-air modulation techniques). This includes at leastWi-Fi (or Wireless Fidelity), WiMax, and Bluetooth™ wirelesstechnologies, among others. Thus, the communication can be a predefinedstructure as with a conventional network or simply an ad hoccommunication between at least two devices. Wi-Fi networks use radiotechnologies called IEEE 802.11x (a, b, g, n, etc.) to provide secure,reliable, fast wireless connectivity. A Wi-Fi network can be used toconnect computers to each other, to the Internet, and to wire networks(which use IEEE 802.3-related media and functions). The wirelesstechnologies may couple to the computer 602 via one or more transceivers(not shown) within for example the optional interface 642 orcommunication interface 656 that facilitate the use of the Wi-Fi, WiMax,Bluetooth wireless technologies as well as others.

The various elements of the devices as previously described withreference to FIGS. 1-6 may include various hardware elements, softwareelements, or a combination of both. Examples of hardware elements mayinclude devices, logic devices, components, processors, microprocessors,circuits, processors, circuit elements (e.g., transistors, resistors,capacitors, inductors, and so forth), integrated circuits, applicationspecific integrated circuits (ASIC), programmable logic devices (PLD),digital signal processors (DSP), field programmable gate array (FPGA),memory units, logic gates, registers, semiconductor device, chips,microchips, chip sets, and so forth. Examples of software elements mayinclude software components, programs, applications, computer programs,application programs, system programs, software development programs,machine programs, operating system software, middleware, firmware,software modules, routines, subroutines, functions, methods, procedures,software interfaces, application program interfaces (API), instructionsets, computing code, computer code, code segments, computer codesegments, words, values, symbols, or any combination thereof. However,determining whether an example is implemented using hardware elementsand/or software elements may vary in accordance with any number offactors, such as desired computational rate, power levels, heattolerances, processing cycle budget, input data rates, output datarates, memory resources, data bus speeds and other design or performanceconstraints, as desired for a given implementation.

As used in this application, the terms “system”, “component” and “unit”are intended to refer to a computer-related entity, either hardware, acombination of hardware and software, software, or software inexecution, examples of which are described herein. For example, acomponent can be, but is not limited to being, a process running on aprocessor, a processor, a hard disk drive, multiple storage drives (ofoptical and/or magnetic storage medium), an object, an executable, athread of execution, a program, and/or a computer. By way ofillustration, both an application running on a server and the server canbe a component. One or more components can reside within a processand/or thread of execution, and a component can be localized on onecomputer and/or distributed between two or more computers.

Further, components may be communicatively coupled to each other byvarious types of communications media to coordinate operations. Thecoordination may involve the uni-directional or bi-directional exchangeof information. For instance, the components may communicate informationin the form of signals communicated over the communications media. Theinformation can be implemented as signals allocated to various signallines. In such allocations, each message is a signal. Further examples,however, may alternatively employ data messages. Such data messages maybe sent across various connections. Exemplary connections includeparallel interfaces, serial interfaces, and bus interfaces.

Some examples may be described using the expression “one example” or “anexample” along with their derivatives. These terms mean that aparticular feature, structure, or characteristic described in connectionwith the example is included in at least one example. The appearances ofthe phrase “in one example” in various places in the specification arenot necessarily all referring to the same example. Moreover, unlessotherwise noted the features described above are recognized to be usabletogether in any combination. Thus, any features discussed separately maybe employed in combination with each other unless it is noted that thefeatures are incompatible with each other.

With general reference to notations and nomenclature used herein, thedetailed descriptions herein may be presented in terms of functionalblocks or units that might be implemented as program procedures executedon a computer or network of computers. These procedural descriptions andrepresentations are used by those skilled in the art to most effectivelyconvey the substance of their work to others skilled in the art.

A procedure, process, or method is here, and generally, conceived to bea self-consistent sequence of operations leading to a desired result.These operations are those requiring physical manipulations of physicalquantities. Usually, though not necessarily, these quantities take theform of electrical, magnetic or optical signals capable of being stored,transferred, combined, compared, and otherwise manipulated. It provesconvenient at times, principally for reasons of common usage, to referto these signals as bits, values, elements, symbols, characters, terms,numbers, or the like. It should be noted, however, that all of these andsimilar terms are to be associated with the appropriate physicalquantities and are merely convenient labels applied to those quantities.

Further, the manipulations performed are often referred to in terms,such as adding or comparing, which are commonly associated with mentaloperations performed by a human operator. No such capability of a humanoperator is necessary, or desirable in most cases, in any of theoperations described herein, which form part of one or more examples.Rather, the operations are machine operations. Useful machines forperforming operations of various examples include general purposedigital computers or similar devices.

Some examples may be described using the expression “coupled” and“connected” along with their derivatives. These terms are notnecessarily intended as synonyms for each other. For example, someexamples may be described using the terms “connected” and/or “coupled”to indicate that two or more elements are in direct physical orelectrical contact with each other. The term “coupled,” however, mayalso mean that two or more elements are not in direct contact with eachother, but still co-operate or interact with each other.

Various examples also relate to apparatus or systems for performingthese operations. This apparatus may be specially constructed for thedescribed purpose or it may comprise a general-purpose computer asselectively activated or reconfigured by a computer program stored inthe computer. The procedures or processes presented herein are notinherently related to a particular computer or other apparatus. Variousgeneral-purpose machines may be used with programs written in accordancewith the teachings herein, or it may prove convenient to construct morespecialized apparatus to perform the required method steps. Thestructure for a variety of these machines appears from the descriptiongiven.

It is emphasized that the Abstract of the Disclosure is provided toallow a reader to quickly ascertain the nature of the technicaldisclosure. It is submitted with the understanding that it will not beused to interpret or limit the scope or meaning of the claims. Inaddition, in the foregoing Detailed Description, various features aregrouped together in a single example to streamline the disclosure. Thismethod of disclosure is not to be interpreted as reflecting an intentionthat the claimed examples require more features than are expresslyrecited in each claim. Rather, as the following claims reflect,inventive subject matter lies in less than all features of a singledisclosed example. Thus, the following claims are hereby incorporatedinto the Detailed Description, with each claim standing on its own as aseparate example. In the appended claims, the terms “including” and “inwhich” are used as the plain-English equivalents of the respective terms“comprising” and “wherein,” respectively. Moreover, the terms “first,”“second,” “third,” and so forth, are used merely as labels, and are notintended to impose numerical requirements on their objects.

What has been described above includes examples of the disclosedarchitecture. It is, of course, not possible to describe everyconceivable combination of components and/or methodologies, but one ofordinary skill in the art may recognize that many further combinationsand permutations are possible. Accordingly, the novel architecture isintended to embrace all such alterations, modifications and variationsthat fall within the spirit and scope of the appended claims.

What is claimed is:
 1. A system, comprising: a payment card comprising apayment card near-field communication device, a rewriteable visualdisplay, a processor, and a memory, wherein the rewriteable visualdisplay of the payment card is operable to present a prior-issued cardnumber; a reissue application stored in a mobile device, wherein thereissue application is executable by a processor of the mobile deviceand when executed is operable to reissue a card number of the paymentcard; and an authentication server operable to communicate with thereissue application, wherein the reissue application, when executed, isfurther operable to: send a request to the authentication server toverify that the reissue application is associated with the payment card;in response to a verification that the reissue application is associatedwith the payment card, obtain an updated card number, wherein theupdated card number is different from the prior-issued card number;generate an updated card number signal including the updated card numberand information related to at least one of: a card verification value,an expiration date, or an issuer; cause the updated card number signalto be output; and wherein the payment card is operable to: receive, viathe payment card near-field communication device, the updated cardnumber signal; and drive, based on the updated card number signal, therewriteable visual display to present an updated card number in place ofthe prior-issued card number.
 2. The system of claim 1, wherein thereissue application, when executed, is further operable to: provide auser interface; receive an input via the user interface; present, viathe user interface, information in response to signals generated by thereissue application; present a menu of selectable user preferences viathe user interface, wherein the selectable user preferences in the menuinclude one or more of: a payment card account balance, a most recenttransaction amount, an annual percentage rate of account, a rewardspoints balance, a payment due date, a location-based discount, or alocation-based reward; receiving, via the user interface, a selection ofat least one selectable user preference from the menu of selectable userpreferences; and storing the at least one selected user preference. 3.The system of claim 2, wherein the reissue application, when executed,is further operable to: in response to a verification that the reissueapplication is associated with the payment card, obtain informationrelated to the selected at least one of the selectable user preferences,wherein the information is retrieved via the authentication server; andgenerate a user preference display signal, wherein the user preferencedisplay signal includes the information related to the selected at leastone of the selectable user preferences; and cause the output of thegenerated user preference display signal to the payment card near-fieldcommunication device.
 4. The system of claim 3, wherein the payment cardis further operable to: receive, via the payment card near-fieldcommunication device, the outputted user preference display signal;process the user preference display signal; and forward the processeduser preference display signal to the rewriteable visual display foroutput of the information related to the selected at least one of theselectable user preferences.
 5. The system of claim 1, wherein thereissue application, when executed, is further operable to: provide auser interface; present, via the user interface, an indication of wherethe payment card is to be placed to enable near-field communicationsignals to be exchanged with the payment card near-field communicationdevice.
 6. The system of claim 1, further comprising: a payment accountserver coupled to a data storage device and communicatively coupled tothe authentication server, wherein the payment account server isoperable to: store payment account information related to the paymentcard, wherein the payment account information includes at least one of:a payment account balance, payment account limits, information relatedto the mobile device, user preference selections, transactioninformation, payment card number history, a list of undeployed paymentcard numbers, or information related to users authorized to use thepayment card.
 7. The system of claim 1, further comprising: a paymentaccount server coupled to a data storage device communicatively coupledto the authentication server, wherein the payment account server isoperable to: in response to a request from the reissue application,retrieve the updated card number from the data storage device; and sendthe updated card number to the reissue application.
 8. The system ofclaim 1, wherein the reissue application is operable to: detect anauthentication signal emitted from the payment card near-fieldcommunication device; forward the authentication signal to theauthentication server; and in response to forwarding the authenticationsignal, receive verification that the payment card is a valid paymentcard associated with the reissue application.
 9. The system of claim 1,wherein: the rewriteable visual display is an electronic ink display,and the payment card near-field communication device transforms theupdated card number signal to voltage values suitable to drive theelectronic ink display to replace the prior-issued card number with theupdated card number.
 10. The system of claim 1, wherein: the paymentcard processor is operable when obtaining the updated card number to:generate an updated card number using a cryptographic hash function anddata maintained in the payment card memory.
 11. The system of claim 1,further comprising: an issuer server communicatively coupled to thereissue application, and wherein the reissue application is furtheroperable when obtaining the updated card number to: retrieve the updatedcard number from an issuer server associated with an issuer of thepayment card.